test: adds pr permissions to bot#29923
Conversation
christopherferreira9
added
the
no-changelog
github-actions
Bot
added
the
pr-not-ready-for-e2e
|
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit eb614f4. Configure here.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #29923 +/- ##
========================================
Coverage 81.50% 81.50%
========================================
Files 5328 5339 +11
Lines 141146 141590 +444
Branches 32157 32272 +115
========================================
+ Hits 115046 115410 +364
- Misses 18239 18280 +41
- Partials 7861 7900 +39 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
christopherferreira9
removed
the
pr-not-ready-for-e2e
|
metamaskbotv2
Bot
added
the
release-7.78.0
3 participants
Description
This PR adds missing permissions for pull-requests to update fixtures that is currently failing with 403.
Changelog
CHANGELOG entry:
Related issues
Fixes: https://consensys.slack.com/archives/CBW7S9FSN/p1778252290987909?thread_ts=1778240496.951059&cid=CBW7S9FSN
Manual testing steps
N/A
Screenshots/Recordings
Before
After
Pre-merge author checklist
Performance checks (if applicable)
trace()for usage andaddTokenfor an exampleFor performance guidelines and tooling, see the Performance Guide.
Pre-merge reviewer checklist
Note
Low Risk
Low risk: only adjusts GitHub Actions job
permissionsfor the comment-triggered dispatcher, with no application/runtime code changes.Overview
Fixes the
Update E2E Fixturesworkflow’s comment-triggereddispatchjob by explicitly grantingactions: writeandpull-requests: write(pluscontents: read) permissions.This allows the bot command (
@metamaskbot update-mobile-fixture) to successfully re-dispatch the workflow onto the PR branch and post PR comments without hitting 403 permission errors.Reviewed by Cursor Bugbot for commit d449d9d. Bugbot is set up for automated code reviews on this repo. Configure here.